IRIX Base Documentation 1998 November

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / u_man / cat1 / rfind.z / rfind

Wrap

Text File | 1998-10-20 | 42KB | 793 lines

RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) NNNNAAAAMMMMEEEE rfind - remote find SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS rrrrffffiiiinnnndddd [----ddddeeeebbbbuuuugggg] file-system search-expression DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _r_f_i_n_d is a fast, client-server adaptation of the _f_i_n_d(1) command. It maps the specified _f_i_l_e-_s_y_s_t_e_m name to a host machine, and submits the _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n to the _r_f_i_n_d_d(1M) daemon running on that host, for evaluation over the specified _f_i_l_e-_s_y_s_t_e_m. The _r_f_i_n_d_d(1M) daemon searches side files for the requested information, and returns it to _r_f_i_n_d(1) for display on stdout. These side files were previously created by the _f_s_d_u_m_p(1M) command, and contain information about a particular _f_i_l_e-_s_y_s_t_e_m If the ----ddddeeeebbbbuuuugggg option is specified, then _r_f_i_n_d will display the result of parsing the _f_i_l_e-_s_y_s_t_e_m and _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n on stdout. FFFFiiiilllleeee----SSSSyyyysssstttteeeemmmm The _f_i_l_e-_s_y_s_t_e_m to be searched may be specified in one of three forms: canonical, alias or local path. Only one _f_i_l_e-_s_y_s_t_e_m may be specified. Remaining arguments are considered to be part of the _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n. If the _f_i_l_e-_s_y_s_t_e_m argument contains a colon ':' character, then it is considered to be in ccccaaaannnnoooonnnniiiiccccaaaallll ffffoooorrrrmmmm. The portion of the name before the first ':' is taken as the network hostname, and the remaining characters after this ':' are taken as the full pathname of the file system subtree to searched. For example, the command: rfind bonnie.wpd:/cypress/att/usr/src foo.c will send a request to the _r_f_i_n_d_d(1M) daemon on the host bonnie.wpd, to search for the file foo.c below the directory /cypress/att/usr/src (staying within whatever file system contains this path). If the _f_i_l_e-_s_y_s_t_e_m argument does not contain a ':' character, then a list of standard locations is searched in an attempt to resolve the _f_i_l_e- _s_y_s_t_e_m as an aaaalllliiiiaaaassss. Four places are searched, in order: 1) the file referenced by the RRRRFFFFIIIINNNNDDDD____AAAALLLLIIIIAAAASSSSEEEESSSS environment variable, if any 2) the file ////eeeettttcccc////rrrrffffiiiinnnndddd....aaaalllliiiiaaaasssseeeessss 3) the NIS (Yellow Pages) map called rfind.aliases 4) a hardwired internal list which aliases "root" and "usr" to "localhost:/" and "localhost:/usr", respectively. The first of these places to specify a mapping for the _f_i_l_e-_s_y_s_t_e_m alias is used. See the comments in the file ////eeeettttcccc////rrrrffffiiiinnnndddd....aaaalllliiiiaaaasssseeeessss for a description of that file's format. PPPPaaaaggggeeee 1111 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) If the _f_i_l_e-_s_y_s_t_e_m argument is neither in canonical form nor an alias, then it is considered to be a llllooooccccaaaallll ppppaaaatttthhhh to either an EFS, XFS or NFS directory or other file. The path need not begin with a slash. Any referenced symbolic links are fully resolved where possible to their final target. The inode named by the local path is examined. If it resides on an "efs" or "xfs" file system, then the request is sent to _r_f_i_n_d_d(1M) on the localhost for resolution. If it resides on an "nfs" file system, then the file ////eeeettttcccc////mmmmttttaaaabbbb is examined to determine the hostname of the server to send the request to. For example, the command: rfind /cypress/att/usr/src foo.c will, in the case that bonnie.wpd:/cypress is mounted to /cypress (or, if /cypress is a symlink, to the target of that symlink), send the same request as the previous example. If the named inode is in an automounted (see _a_u_t_o_m_o_u_n_t(1M)) file system, then that file system will be automounted if it wasn't already. The local mount point need not be isomorphic with the server's pathname for this file system. If none of these mechanisms succeeds, then _r_f_i_n_d(1) displays a list of all known aliases on its error output and exits with non-zero status. SSSSeeeeaaaarrrrcccchhhh----EEEExxxxpppprrrreeeessssssssiiiioooonnnn _r_f_i_n_d accepts a boolean _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n, written in the primaries given below, that has a syntax similar to that of the _f_i_n_d(1) command. In the descriptions, the argument _n is used as a decimal integer where ++++_n means strictly greater than _n, ----_n means strictly less than _n and _n means exactly _n. Valid expressions are: ----nnnnaaaammmmeeee _f_i_l_e True if _f_i_l_e matches as many trailing components of the current file's pathname as are specified in the pattern _f_i_l_e. The wildcard characters [[[[, !!!!, ----, ???? and **** may be used to specify filename patterns. See the section _F_i_l_e _N_a_m_e _G_e_n_e_r_a_t_i_o_n of _s_h(1) for their usage. If the first character of _f_i_l_e is the slash //// character, then all components of the current file's pathname must match. ----rrrrooooooootttt _p_a_t_h True if the current file is located in the _f_i_l_e-_s_y_s_t_e_m hierarchy somewhere under the directory specified by _p_a_t_h. If _p_a_t_h specifies a file that is not a directory, then this primary is true for just that specified file. ----ppppeeeerrrrmmmm [----]_o_n_u_m True if the file permission flags exactly match the octal number _o_n_u_m (see _c_h_m_o_d(1)). If _o_n_u_m is prefixed by a minus sign, only the bits that are set in _o_n_u_m are compared with the file permission flags, and the expression evaluates true if they match. PPPPaaaaggggeeee 2222 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) ----ttttyyyyppppeeee _c True if the type of the file is _c, where _c is bbbb, cccc, dddd, llll, pppp, ffff, or ssss for block special file, character special file, directory, symbolic link, fifo (a.k.a named pipe), plain file, or socket respectively. ----lllliiiinnnnkkkkssss _n True if the file has _n links. ----uuuusssseeeerrrr _u_n_a_m_e True if the file belongs to the user _u_n_a_m_e. If _u_n_a_m_e is numeric and does not appear as a login name in the ////eeeettttcccc////ppppaaaasssssssswwwwdddd file, it is taken as a decimal user ID. ----ggggrrrroooouuuupppp _g_n_a_m_e True if the file belongs to the group _g_n_a_m_e. If _g_n_a_m_e is numeric and does not appear in the ////eeeettttcccc////ggggrrrroooouuuupppp file, it is taken as a decimal group ID. ----ssssiiiizzzzeeee _n[cccc] True if the file is _n blocks long (512 bytes per block). If _n is followed by a cccc, the size is in characters. ----iiiinnnnuuuummmm _n True if _n is the inode number of the file. If -_i_n_u_m is used to display a single inode (that is, if the _n inode number specified is not prefixed with a ++++ or ----), and if the current inode has multiple links, then the pathname of only one of the links is available for printing. ----aaaattttiiiimmmmeeee _n True if the file has been accessed in _n days (see _s_t_a_t(2) for a description of which file operations change the access time of a file). ----mmmmttttiiiimmmmeeee _n True if the file has been modified in _n days (see _s_t_a_t(2) for a description of which file operations change the modification time of a file). ----ccccttttiiiimmmmeeee _n True if the file has been changed in _n days (see _s_t_a_t(2) for a description of which file operations change the change time of a file). ----pppprrrriiiinnnntttt Always true; causes the current path name to be printed. ----llllssss Always true; causes current pathname to be printed together with its associated statistics. These include (respectively) inode number, protection mode, number of hard links, user, group, size in bytes, and modification time. If the file is a special file the size field will instead contain the major and minor device numbers. If the file is a symbolic link the pathname of the linked-to file is printed preceded by ->. The format is identical to that of _l_s -_l_i_d, however the formatting is done internally, without executing the _l_s program. ----pppprrrriiiinnnnttttffff _f_o_r_m_a_t Always true; causes information about the current file to be printed using the specified _f_o_r_m_a_t. The _f_o_r_m_a_t is a character string that contains three kinds of objects: PPPPaaaaggggeeee 3333 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) 1) plain characters, which are simply copied to the output stream, 2) the C-like escape sequences \\\\bbbb, \\\\ffff, \\\\nnnn, \\\\rrrr, \\\\tttt and \\\\vvvv, which are converted (see _e_c_h_o(1) for their meaning), and 3) conversion specifications, each of which results in displaying in decimal or string form the value of a particular attribute of the current file. The conversion specifications recognized are described below in the section _P_r_i_n_t_f _F_o_r_m_a_t. ----nnnncccchhhheeeecccckkkk _n True if _n is the inode number of the current file. Causes the inode number and full pathname for each link to the current file to be displayed in the fixed format "%i\t%P\n" for each link to the current file. The output resembles that from the _n_c_h_e_c_k(1) command. ----nnnnoooonnnneeee Always true; suppresses the default ----pppprrrriiiinnnntttt operator in the case that none of the operators ----llllssss, ----pppprrrriiiinnnntttt, ----pppprrrriiiinnnnttttffff, or ----nnnncccchhhheeeecccckkkk were supplied. ----nnnneeeewwwweeeerrrr _p_a_t_h True if the current file has been modified more recently than the argument _p_a_t_h. The file specified by _p_a_t_h must be root based, and reference a file within the _f_i_l_e- _s_y_s_t_e_m that is being searched. See _s_t_a_t(2) for a description of which file operations change the modification time of a file. ----aaaannnneeeewwwweeeerrrr _p_a_t_h True if current file has been accessed more recently than the argument _p_a_t_h. The file specified by _p_a_t_h must be root based, and reference a file within the _f_i_l_e-_s_y_s_t_e_m that is being searched. See _s_t_a_t(2) for a description of which file operations change the access time of a file. ----ccccnnnneeeewwwweeeerrrr _p_a_t_h True if current file has been changed more recently than the argument _p_a_t_h. The file specified by _p_a_t_h must be root based, and reference a file within the _f_i_l_e-_s_y_s_t_e_m that is being searched. See _s_t_a_t(2) for a description of which file operations change the change time of a file. ----ddddeeeepppptttthhhh Always true; causes descent of the directory hierarchy to be done so that all entries in a directory are acted on before the directory itself. ----pppprrrruuuunnnneeee Always true; has the side effect of pruning the search tree at the current file. If the current path name is a directory, _r_f_i_n_d will not descend below directory. ----ffffoooolllllllloooowwww Always true; causes the underlying file of a symbolic link to be checked rather than the symbolic link itself. ----sssshhhhoooowwwwddddoooottttssss Always true; causes the conventional "." and ".." entries of each directory to become visible. Normally these entries are suppressed unless explicitly named by path or PPPPaaaaggggeeee 4444 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) inode number. ----cccchhhhaaaannnnggggeeeedddd True if executing the _s_t_a_t(2) system call from the _r_f_i_n_d_d(1M) daemon on the full pathname of the current file yields a result that does not have the same file type, modification time, change time and size values as were observed for the current file when it was last examined by _f_s_d_u_m_p(1M). In the case that the current file is a directory, then the logic of the ----cccchhhhaaaannnnggggeeeedddd operator is optimized for use by _p_t_o_o_l_s(1), a software source control tool used internally by Silicon Graphics, and involves executing the _s_t_a_t(2) system call for every directory that contains any link (hard or symbolic) of any file contained within the current directory. ----nnnneeeewwwwddddiiiirrrraaaadddddddd ffffoooorrrrmmmmaaaatttt True if executing the _s_t_a_t(2) system call from the _r_f_i_n_d_d(1M) daemon on the full pathname of the current file yields a result that does not have the same file type, modification time, change time and size values as were observed for the current file when it was last examined by _f_s_d_u_m_p(1M) and that it is a directory which contains subdirectories which previously did not exist or were of a different type. The information about these directories is printed using the specified format. ----ssssttttccccoooouuuunnnntttt Always true; subtree count - increments running subtree total by a count of one. The subtree options are described below in the section _S_u_b_t_r_e_e _O_p_t_i_o_n_s. ----ssssttttssssiiiizzzzeeee Always true; subtree size - increments running subtree total by the number of blocks in the current file. The subtree options are described below in the section _S_u_b_t_r_e_e _O_p_t_i_o_n_s. ----ssssttttttttoooottttaaaallll _t_h_r_e_s_h_o_l_d True if the running subtree total exceeds the specified decimal _t_h_r_e_s_h_o_l_d, or if the running subtotal is non-zero and the current path being evaluated is the final, root path. If true, copies the running subtotal to the aggregate subtotal, and zeros the running subtotal. The subtree options are described below in the section _S_u_b_t_r_e_e _O_p_t_i_o_n_s. ----eeeexxxxiiiitttt _s_t_a_t_u_s If executed during the course of evaluating the _s_e_a_r_c_h- _e_x_p_r_e_s_s_i_o_n, causes _r_f_i_n_d(1) to exit immediately with the specified decimal _s_t_a_t_u_s. (((( _e_x_p_r_e_s_s_i_o_n )))) True if the parenthesized expression is true (parentheses are special to the shell and must be escaped). PPPPaaaaggggeeee 5555 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) The primaries may be combined using the following operators (in order of decreasing precedence): 1) The negation of a primary (!!!! is the unary _n_o_t operator). 2) Concatenation of primaries (the _a_n_d operation is implied by the juxtaposition of two primaries). The _a_n_d operator may also be specified as ----aaaa. 3) Alternation of primaries (----oooo is the _o_r operator). PPPPrrrriiiinnnnttttffff FFFFoooorrrrmmmmaaaatttt This section describes the conversion specifications accepted by the ----pppprrrriiiinnnnttttffff _f_o_r_m_a_t option. Each conversion specification consists of the character %%%% and a single following conversion character. Numeric quantities are output in decimal, except for permissions, which are octal. The conversion specifications and their meanings are: %%%%aaaa,%%%%cccc,%%%%mmmm The access (atime), change (ctime) or modification (mtime) time stamps for the current file, as seconds since the epoch. %%%%uuuu,%%%%gggg The numeric user (uid) or group (id) for the current file. %%%%pppp The octal permissions (mode, including type) for the current file. %%%%nnnn The number of links to the current file. %%%%iiii The inode number of the current file. %%%%ssss The size in bytes of the current file. %%%%eeee The NFS internal generation number (gen) of the current file. %%%%dddd For block and character special files, the major/minor device (rdev) of the current file. For other file types, this is zero. %%%%xxxx For directory and regular files, the number of EFS extents. For other file types, this is zero. %%%%NNNN The actual number of links observed when _f_s_d_u_m_p(1M) traversed the _f_i_l_e-_s_y_s_t_e_m. This will usually be the same value as for %%%%nnnn, above, unless either a concurrent update caused inconsistent data to be captured (rare but allowed), or _f_s_d_u_m_p(1M) lacked permissions to scan part of the directory structure (in which case, inode contents are still available, but names are not). The _f_s_d_u_m_p(1M) command runs setuid root only long enough to obtain a read only file descriptor on the target _f_i_l_e-_s_y_s_t_e_m in order to read inode contents, then PPPPaaaaggggeeee 6666 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) restores its invoker's privileges. %%%%EEEE For directories, the number of directory entries observed when _f_s_d_u_m_p(1M) traversed the _f_i_l_e-_s_y_s_t_e_m. %%%%SSSS The number of active inodes below this inode in the _f_i_l_e-_s_y_s_t_e_m hierarchy. This value is only non-zero for directories. The conventional "." and ".." directory entries are included in this count. %%%%IIII The total number of active inodes in the _f_i_l_e-_s_y_s_t_e_m. %%%%MMMM The pathname of the mount point on which the current _f_i_l_e- _s_y_s_t_e_m was mounted when _f_s_d_u_m_p examined it. %%%%QQQQ One of the "file environment" attributes: a quick and dirty checksum of just the first 8 bytes of each 512 block of the file, plus the inode number of the file. %%%%YYYY One of the "file environment" attributes: If the current file is a symbolic link, displays the path contained in the link file. If the file is not a symbolic link, or its contents could not be read by _f_s_d_u_m_p(1M), then displays the empty string. %%%%UUUU Aggregate subtree total - see further the section _S_u_b_t_r_e_e _O_p_t_i_o_n_s. %%%%RRRR One of the "file environment" attributes: the top-of-trunk RCS delta number. This value is maintained for files that appear to be RCS ,v files, and is the empty string for other files. %%%%TTTT One of the "file environment" attributes: the top-of-trunk RCS date stamp. This value is maintained for files that appear to be RCS ,v files, and is the empty string for other files. %%%%LLLL One of the "file environment" attributes: the user name of the locker of locked RCS ,v files. For any other file, this is the empty string. %%%%AAAA One of the "file environment" attributes: the user name of the author of the RCS top-of-trunk delta. For other files, this is the empty string. %%%%DDDD The pathname of the directory containing the current file, or dirname. %%%%BBBB The basename of the current file. %%%%PPPP The full pathname of the current file. PPPPaaaaggggeeee 7777 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) %%%%WWWW The canonical full pathname of the current file. If the _f_i_l_e- _s_y_s_t_e_m argument to _r_f_i_n_d passes through a symlink, then the "%P" format will show you a pathname relative to the path provided in the _f_i_l_e-_s_y_s_t_e_m argument, whereas "%W" will show you the canonical pathname, free of symlinks. %%%%ZZZZ The full pathname of the new subdirectory within the current file. %%%%%%%% Same as %. SSSSuuuubbbbttttrrrreeeeeeee OOOOppppttttiiiioooonnnnssss The ----ssssttttccccoooouuuunnnntttt, ----ssssttttssssiiiizzzzeeee and ----ssssttttttttoooottttaaaallll options, together with the ----pppprrrriiiinnnnttttffff "%U" format, provide a mechanism to group subtrees of the searched tree by sizes or counts. The ----ssssttttttttoooottttaaaallll option implies the ----ddddeeeepppptttthhhh option. The _r_f_i_n_d command maintains two internal values, the running subtotal and the aggregate subtotal. Both values are initialized to zero. The running subtotal is maintained during the recursive depth first search so that for directories it is always the total values not already aggregated for the subtree below the directory, and for other files, it is always the value for just that file. The aggregate subtotal is reset to zero before evaluating the _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n for each file. Whenever the ----ssssttttccccoooouuuunnnntttt option is evaluated, it increments the running subtotal by one. Whenever the ----ssssttttssssiiiizzzzeeee option is evaluated, it increments the running subtotal by the size in blocks of the current file. Whenever, for an individual file or for a subtree, the ----ssssttttttttoooottttaaaallll option is evaluated and the current running subtotal exceeds the _t_h_r_e_s_h_o_l_d specified on the ----ssssttttttttoooottttaaaallll option, then the running subtotal is copied to the aggregate subtotal, and the running subtotal is reset to zero. When evaluating the _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n for the final (top) directory of the search (namely, the directory specified or implied by the ----rrrrooooooootttt option), the ----ssssttttttttoooottttaaaallll option copies any non-zero running subtotal to the aggregate subtotal, even if it does not exceed the specified _t_h_r_e_s_h_o_l_d, and evaluates as true if a copy was done. The ----pppprrrriiiinnnnttttffff "%U" format displays the current value of the aggregate subtotal. These options are intended to be used together. Typically one of either the ----ssssttttccccoooouuuunnnntttt or ----ssssttttssssiiiizzzzeeee option is used to increment the running subtotal, along with the ----ssssttttttttoooottttaaaallll option to copy the running subtotal to the aggregate subtotal whenever the threshold is reached, along with the ----pppprrrriiiinnnnttttffff "%U" format to display the aggregate subtotal. For example, one could determine where, in a large RCS based source tree, the recent (say, in the last day) changes to RCS/*,v files were clustered, with the command: PPPPaaaaggggeeee 8888 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) rfind cypress 'RCS/*,v' -mtime -1 -stcount -o -type d -sttotal 10 -printf "%U\t%P\n" The output from the above command might look like: 14 /cypress/att/usr/src/cmd/motif/clients/4Dwm/RCS 13 /cypress/att/usr/src/cmd/motif/sgi/book 12 /cypress/att/usr/src/cmd/X11R4/mit/fonts.pcf/bdf/75dpi/RCS 16 /cypress/att/usr/src/cmd/X11R4/mit 17 /cypress/att/usr/src/cmd/demo 14 /cypress/att/usr/src/cmd 11 /cypress/att/usr/src/man 10 /cypress/att/usr/src/gfx/lib/libgl/LIGHT/asmgfx/RCS 11 /cypress/att/usr/src/gfx/lib/libgl/LIGHT/cgfx/RCS 14 /cypress/att/usr/src/gfx 32 /cypress/att/usr/src 10 /cypress/bsd/src/etc/timed/RCS 1 /cypress The above output shows the several subtrees containing 10 or more changed RCS/*,v files, with the number of such files in the first column. For another example, one could determine where disk space was being used on the root file system with the command: rfind root -stsize -sttotal 1000 -printf "%U\t%P\n" This command produces output like the following: 1374 /bin/wsh 1201 /bin/news_server 4991 /bin 3551 /etc/gl 3651 /etc 2192 /stand/ide 2817 /unix 1961 / From this output, one can see that three individual files, /bin/wsh, /bin/news_server and /unix, exceeded the 1000 block threshold, that most of the remaining disk space is in use by files under the directories /bin, /etc/gl, /etc and /stand/ide, and that 1961 blocks of data resides somewhere else on the root file system. DDDDeeeeffffaaaauuuullllttttssss To make interactive use easier, _r_f_i_n_d supports several default options and primaries in the _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n. 1) A default leading option of ----rrrrooooooootttt ////rrrroooooooottttppppaaaatttthhhh is supplied, where /rootpath is the mount point implied by the first argument to _r_f_i_n_d. PPPPaaaaggggeeee 9999 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) 2) The _s_e_a_r_c_h-_e_x_p_r_e_s_s_i_o_n is parsed from left to right in two phases. 3) Unexpected arguments in the first phase that begin with the '////' character are supplied a default ----rrrrooooooootttt option. 4) The ----rrrrooooooootttt _p_a_t_h primaries constructed during the first phase are automatically separated from each other by the ----oooo operator. 5) The first phase ends at the first argument that is neither an explicit ----rrrrooooooootttt nor starts with the '////' character. 6) At the end of the first phase, an automatic opening (((( parenthesis is inserted, so that the entire list of ----oooo separated roots just built is concatenated (implying the ----aaaa operator) with the expression resulting from the second phase. 7) Unexpected arguments in the second phase that do not begin with the '----' character are supplied a default ----nnnnaaaammmmeeee option. 8) At the end of the second phase, sufficient closing )))) parentheses are supplied to match any unmatched opening (((( parentheses. 9) Finally, if none of the operators ----llllssss, ----pppprrrriiiinnnntttt, ----pppprrrriiiinnnnttttffff, ----nnnnoooonnnneeee or ----nnnncccchhhheeeecccckkkk appeared, a default ----pppprrrriiiinnnntttt operator is supplied. The result of the above defaults is that the command: rfind cypress ed.c is automatically expanded into the equivalent command: rfind cypress -root /cypress -a $ -name ed.c $ -print and that the command: rfind bugs /d1/Bugs /d1/alphabugs 1234 is automatically expanded into the command: rfind bugs -root /d1 -a $ -root /d1/Bugs -o -root /d1/alphabugs $ -a $ -name 1234 $ -print PPPPeeeerrrrffffoooorrrrmmmmaaaannnncccceeee The _r_f_i_n_d_d (_1_M) daemon dynamically selects from several available search strategies in order to provide optimum performance. 1) The ----rrrrooooooootttt _p_a_t_h option may be used to specify a small portion of the _f_i_l_e-_s_y_s_t_e_m to be searched. 2) The ----nnnnaaaammmmeeee _f_i_l_e option may take advantage of a secondary sort index by file basename. The first wildcard character [[[[, ???? or **** in the basename of the provided name terminates the portion of the basename PPPPaaaaggggeeee 11110000 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) which is used to restrict the search. 3) If the ----iiiinnnnuuuummmm _n or ----nnnncccchhhheeeecccckkkk _n options are used, then direct and rapid lookup is possible. 4) If the either of the options ----pppprrrruuuunnnneeee or ----ddddeeeepppptttthhhh are used, then this disables the above search strategies (2) by name and (3) by inode number. Small searches that are able to take advantage of one of the above search strategies often complete in less than 1 second. Large searches that require walking a large tree can take up to several minutes, depending primarily on server performance. The selection of search strategy is based on dynamically computed weights, so two _r_f_i_n_d(1) commands that are syntactically identical may be accomplished by different strategies depending for example on the relative size of the subtrees specified by ----rrrrooooooootttt _p_a_t_h options and the relative portion of the name space covered by ----nnnnaaaammmmeeee _f_i_l_e options. The order of output is dependent on the search order. In the case that the secondary sort index by file basename is used, the output will not appear to have any particular order. CCCCoooommmmppppaaaarrrriiiissssoooonnnn ttttoooo ffffiiiinnnndddd((((1111)))) The _r_f_i_n_d(1) has the following new options that are not available in the _f_i_n_d(1) command: ----rrrrooooooootttt, ----llllssss, ----pppprrrriiiinnnnttttffff, ----nnnnoooonnnneeee, ----nnnncccchhhheeeecccckkkk, ----sssshhhhoooowwwwddddoooottttssss, ----ssssttttccccoooouuuunnnntttt, ----ssssttttssssiiiizzzzeeee, ----ssssttttttttoooottttaaaallll, ----cccchhhhaaaannnnggggeeeedddd and ----eeeexxxxiiiitttt. The following _f_i_n_d(1) options are not available in _r_f_i_n_d(1): ----ccccppppiiiioooo, ----ooookkkk, ----eeeexxxxeeeecccc, ----llllooooccccaaaallll and ----mmmmoooouuuunnnntttt. Since the preferred way to create cpio archives is to use the _c_p_i_o(1) command itself, perhaps receiving filenames via a pipe from the _f_i_n_d(1) command, it did not seem worthwhile to maintain the obsolete variant of _c_p_i_o that is embedded in the _f_i_n_d(1) command. Since the _r_f_i_n_d(1) uses _r_p_c(3R) with minimal authentication, the ----ooookkkk and ----eeeexxxxeeeecccc options would have presented unacceptable security compromises. Since the _r_f_i_n_d(1) command only works on a single _f_i_l_e- _s_y_s_t_e_m, the ----llllooooccccaaaallll and ----mmmmoooouuuunnnntttt options are effectively always on. The _f_i_n_d(1) searches in realtime on multiple file systems, whereas _r_f_i_n_d(1) searches the previously created side file of a single file system. The _f_i_n_d(1) command is a single process utility, whereas the _r_f_i_n_d(1) command is the frontend of client-server utility. Searching a large file system is many times faster with _r_f_i_n_d(1) than with _f_i_n_d(1). The ----nnnnaaaammmmeeee _f_i_l_e option of _r_f_i_n_d(1) supports multiple components in the pattern _f_i_l_e. PPPPaaaaggggeeee 11111111 RRRRFFFFIIIINNNNDDDD((((1111)))) RRRRFFFFIIIINNNNDDDD((((1111)))) The command line defaults simplify the use of _r_f_i_n_d(1). EEEExxxxaaaammmmpppplllleeeessss To find all files named 'find*' in Cypress: rfind cypress 'find*' To display all character special devices on the root file system except those under any ddddeeeevvvv directory: rfind root -type d -name dev -prune -o -type c -print To find all symbolic links that point off the current file system (or point nowhere): rfind cypress -follow -type l To display the grand total number of blocks contained in all files and (recursively) directories within a directory subtree rooted at $P, where $P is the canonical (symlink free) absolute (root based) path to the top of the subtree: rfind $P -stsize $P -sttotal 1 -printf "%U\t%P\n" The output of the above command is similar to the output of: du -s $P FFFFIIIILLLLEEEESSSS /etc/rfind.aliases List of _f_i_l_e-_s_y_s_t_e_m mappings. /etc/passwd UID information supplier /etc/group GID information supplier SSSSEEEEEEEE AAAALLLLSSSSOOOO chmod(1), cpio(1), echo(1), find(1), fsdump(1M), ncheck(1), rfindd(1M), sh(1), test(1). stat(2), umask(2), rpc(3R), fs(4). BBBBUUUUGGGGSSSS Do not use the ----pppprrrruuuunnnneeee option with either of the ----ddddeeeepppptttthhhh or ----ssssttttttttoooottttaaaallll options, because the alternative tree walk order used by these options confuses the logic of the ----pppprrrruuuunnnneeee option, causing the wrong _f_i_l_e-_s_y_s_t_e_m subtree to be pruned. PPPPaaaaggggeeee 11112222